System and method for optimizing network communication in response to network conditions

ABSTRACT

A system and method for facilitating communications between a mobile device and a network application are provided. A mobile device transmits a request for data change information that includes a time out interval. The network application receives the request and measures a time elapsed since the receipt of the data change request. The network application will only transmit a notification to the mobile device client if new data is received or the time out interval has elapsed. As notifications are received, the mobile client device tunes the time out interval based upon network and device parameters.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Patent Application No. 60/577,615, entitled SYSTEM AND METHOD FOR OPTIMIZING NETWORK COMMUNICATION IN RESPONSE TO NETWORK CONDITIONS, and filed on Jun. 7, 2004. U.S. Patent Application No. 60/577,615 is incorporated by reference herein.

FIELD OF THE INVENTION

In general, the present invention relates to mobile devices, computer software and communication devices, and in particular, to a system and method for optimizing network communication in response to network conditions.

BACKGROUND OF THE INVENTION

Generally described, mobile devices, such as mobile telephones and hand-held devices, utilize communication networks to exchange data with other mobile devices and/or computer devices. In a typical embodiment, a mobile device can utilize a wireless communication network, and various network protocols, to transmit and receive data. In such an embodiment, a mobile device can maintain continuous, or semi-continuous, wireless connections to allow a user with a mobile device to receive and transmit electronic mail. As the computing device processing resources and wireless network communication bandwidth continue to increase, the use of wireless enabled mobile devices to receive/transmit electronic mail has substantially increased.

FIG. 1 is a block diagram illustrative of a system 100 for facilitating the transmission of electronic mail data to a mobile device via a cellular communication network. The system 100 is generally referred to as a “push” data model, in which data, such as electronic mail messages, is transmitted to a client as the data is received. With reference to FIG. 1, the system 100 includes a plurality of clients 102, such as mobile telephones, hand-held devices, etc., that include some form of wireless (e.g., cellular) transmission capability. As illustrated in FIG. 1, each of the mobile devices 102 is in wireless communication with one of several mobile device operators 104. Generally described, a mobile device operator 104 is a service provider that maintains radio frequency-based communication with any number of mobile devices 102. The wireless communication between the mobile devices 102 and the mobile device operator 104, such as via a cellular communication network, is well known and will not be described in greater detail.

With continued reference to FIG. 1, each mobile device operator 104 is also in communication with a data service provider 106. A typical data service provider 106 can be a server computer configured to transmit messages corresponding to identified mobile users. As will be explained in greater detail below, the data service provider 106 monitors for incoming data (e.g., electronic mail messages) and pushes the data to a corresponding mobile operator 104 for transmission to a selected mobile device 102. The network connection between the data service provider 106 and the mobile operators 104 may be via a wireless communication network and/or a wired communication network. The data service provider 106 is also in communication with a number of electronic mail interface computing devices 108. The electronic mail interface computing devices 108 generally correspond to specially configured computing devices that serve as an interface between a local network mail repository 110 and the data service provider 106.

In practice, as updated information, such as a new electronic mail, is received at the network mail repository 110, the electronic mail interface computing device 108 obtains a copy of the mail and forwards a notification to the data service provider 106. The data service provider 106 processes the incoming message notifications and identifies the mobile device 102 that is to receive the mail. The data service provider 106 then forwards a notification and/or the mail to a corresponding mobile operator 104, which transmits the information to the selected mobile device 102.

In this approach, the mobile device 102 receives notifications/data as the data is received by the data service provider 106. Although this approach provides a real-time, or substantially real-time, transmission of data to a mobile device 102, it requires a number of specialized computing device applications and/or specialized business relationships. For example, in a typical embodiment, each local network is required to maintain an electronic mail interface computing device 108 to forward incoming message notifications to the data service provider 106. Additionally, the system 100 requires a centralized information collection and distribution center (e.g., data service provider 106), which typically charges a service fee to each mobile device user. Further, this approach requires the data service provider 106 to maintain appropriate communication interfaces, such as specialized software, and specialized business relationships with a number of mobile operators to allow the data service provider to initiate contact with a selected mobile device 102.

FIG. 2 is a block diagram illustrative of an alternate system 200 for facilitating the transmission of electronic mail data to a mobile device via a cellular communication network. The system 200 is generally referred to as a “pull” data model, in which data, such as electronic mail messages, is transmitted to a client, such as a mobile device, in response to a request for new data by the client. Similar to system 100 (FIG. 1), the system 200 includes a plurality of mobile device clients 202, that have some form of wireless transmission capability (e.g., cellular communication capabilities). Each of the mobile devices 202 is in wireless communication with one of several mobile device operators 204. In this embodiment, however, the wireless communication link between the mobile device operator 204 and each mobile device 202 is not a specialized communication link for transmitting electronic mail messages. Instead, the communication link is a traditional data transmission communication link with a wide area network 206, such as the Internet. For example, in one common embodiment, a wireless enabled mobile device 202 can transmit data across the Internet in accordance with the Transmission Control Protocol (TCP)/Internet Protocol (IP) protocol. The mobile devices 202 utilize the network connection 206 to interface directly with the local electronic mail interface computing devices 208.

In practice, the mobile device 202 establishes a communication link with the electronic mail interface computing device 208, typically through a secure data transmission protocol. The mobile device 202 then transmits a request to receive any updated information (e.g., new electronic mail) directly to the electronic mail interface computing device 208. If there is new data for the mobile device user, the electronic mail interface computing device 208 generates an appropriate response that instructs the mobile device 102 to pull the data from the electronic mail interface computing device 208. If there is not new data, the electronic mail interface computing device 208 generates a negative response to the requesting mobile device 202. Once the mobile device request is processed, the communication link between the mobile device 202 and the electronic mail interface computing device 208 is terminated.

By allowing a direct communication channel between the mobile devices 202 and the electronic mail interface computing devices 208 over a network connection, the system 200 mitigates the need for specialized software/computing devices for each local network and at each mobile operator 204. However, conventional systems using a “pull” data model can become deficient in that incoming data may not be delivered contemporaneously as the data is received. Although this deficiency may be reduced by increasing the frequency in which the mobile devices 204 generate the above described data change requests, the typical methodology for establishing a communication link between a mobile device 204 and the electronic mail interface computing device 208 consumes power resources from the mobile device.

Thus, there is a need for a system and method for facilitating communication between a computing device and a network application that delivers incoming data notifications contemporaneously as the data is received while mitigating the need for specialized software/computing devices for each network.

SUMMARY OF THE INVENTION

A system and method for facilitating communications between a mobile device and a network application are provided. A mobile device transmits a request for data change information that includes a time out interval. The network application receives the request and measures a time elapsed since the receipt of the data change request. The network application will only transmit a notification to the mobile device client if new data is received or the time out interval has elapsed. As notifications are received, the mobile client device tunes the time out interval based upon network and device parameters.

In accordance with an aspect of the present invention, a method for facilitating communication between a mobile device and a network application is provided. In accordance with the method, a network application obtains a request for change of data. The request for change of data includes a first set of expiration data for returning a response. The network application monitors a time interval for providing a response to the request for change of data. Additionally, the network application, transmits a notification that no data has changed if the time interval exceeds an expiration period.

In accordance with another aspect of the present invention, a method for facilitating communications between a mobile device and a network application is provided. In accordance with the method, a mobile device transmits a first request for change of data. The first request for change of data includes a first set of expiration data for returning a response. The mobile device then determines an event corresponding to the first request for change of data. The mobile device generates a second set of expiration data for returning a response based upon at least one network condition. Additionally, the mobile device transmits a second request for change of data. The second request for change of data includes the second set of expiration data for returning a response.

In accordance with a further aspect of the present invention, a system for facilitating data exchange is provided. The system includes one or more client devices for generating a request for change of data. The request for generating a change of data includes a first expiration time period. The system further includes at least one network application for receiving the request for change of data and transmitting a notification that no data has changed if a monitored time period corresponding to the first expiration time period has expired. The one or more client devices transmit a subsequent request for change of data if an event has occurred. The subsequent request for change of data includes a second expiration time period.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram of a system for facilitating the transmission of electronic mail data to a mobile device via a cellular communication network in accordance with a push data model;

FIG. 2 is a block diagram of a system for facilitating the transmission of electronic mail to a mobile device via a cellular communication network in accordance with a pull data model;

FIG. 3A is a block diagram of the system of FIG. 2 illustrating the generation of a data change request by a mobile device including a time out interval in accordance with an aspect of the present invention;

FIG. 3B is a block diagram of the system of FIG. 2 illustrating the transmission of a notification of a data change by a network application in accordance with an aspect of the present invention;

FIG. 3C is a block diagram of the system of FIG. 2 illustrating the transmission of a time out interval expiration notification by a network application in accordance with an aspect of the present invention;

FIG. 3D is a block diagram of the system of FIG. 2 illustrating the processing of a time out interval expiration by a mobile device in accordance with an aspect of the present invention;

FIG. 4 is a flow diagram illustrative of a data change request transmission and monitoring routine implemented by a mobile device client in accordance with an aspect of the present invention;

FIG. 5 is flow diagram illustrative of time out interval tuning sub-routine implemented by a mobile device client in accordance with an aspect of the present invention;

FIG. 6 is a flow diagram illustrative of client data change request processing routine implemented by a network application in accordance with the present invention; and

FIG. 7 is a block diagram of a system for facilitating the transmission of electronic mail to a mobile device via a cellular communication network and a separate notification channel in accordance with an aspect of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Generally described, the present invention relates to a system and method for optimizing communication between a client device and a network application. More specifically, the present invention is directed toward a system and method for optimizing communication between a mobile device and a network application via a wireless network. The present invention will be described with regard to an architecture incorporating a pull data model in which the mobile device requests data change information in the form of electronic mail messages from a network application. Further, the present invention will be described with regard to the utilization of a time out interval to maintain a communication link between a mobile device and a network application. Although the present invention will be described with regard to a mobile devices, wireless communication networks, and/or electronic mail transmissions, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting.

In an illustrative embodiment of the present invention, a system implementing a pull data model, such as system 200 (FIG. 2), may be utilized to facilitate the transmission of information between a client, such as a mobile device 202, and a network application, such as an electronic mail interface computing device 208. The mobile device 202 and the electronic mail interface computing device 208 transmit information via a typical network data connection 206, such as the Internet. The connection from the network 206 to the mobile device 202 may be facilitated through a mobile device operator 204 (e.g., a data connection via a wireless communication link) or via a direct wireless connection to the network (e.g., a Bluetooth protocol wireless connection).

In accordance with the present invention, a mobile device issues a data change request to the electronic mail interface computing device 208. The data change request can include a registration request for new data that has arrived at the electronic mail interface computer device 208 (e.g., a new email message) and a time-out interval. The time-out interval specifies a time in which the electronic mail interface computing device 208 is required to provide a positive or negative response to the registration request for new data. Unlike traditional data change requests, the electronic mail interface computing device 208 does not provide an immediate response to the data change request if no new data is available. Instead, the electronic mail interface computing device 208 maintains a communication link with the mobile device 202 until it detects an information change (e.g., the arrival of new electronic mail) or the expiration of the time out interval. Upon occurrence of either event, the electronic mail interface computing device 208 transmits an appropriate response to the mobile device 202. In turn, the mobile device 202 can update the time-out interval according to various network conditions and sends a subsequent data change request with the updated time out interval. By maintaining communication even when no data has been received, the electronic mail interface computing device 208 prevents the termination of the communication link with the mobile device 202.

With reference now to FIGS. 3A-3D, various embodiments for processing a client request having a time out interval in accordance with the present invention will be described. With reference to FIG. 3A, the process is initiated by the generation of a registration request and time out interval by a client on a mobile device. In an illustrative embodiment of the present invention, the registration request can include the registration of the type of information the client wishes to receive and various configuration information, such as notification preferences, client authentication information, and the like. As will be described in greater detail below, the time out interval may be in the form of a fixed time period or as a set of criteria that allows for the calculation of a time out interval. The time out interval may be a default period set by the mobile device client application, the mobile device operator 204 and the electronic mail interface computing device 208. For example, a mobile device operator 204 may maintain their own time out interval that will result in a dropped communication link if no data is passed between the mobile device 202 and the electronic mail interface computing device 208 during the mobile device operator-specified time out interval. Accordingly, a default time out interval would likely be of a value less than the time out interval specified by the particular mobile device operator 204 used by the mobile device 202. The registration request and time out interval is transmitted over the network 206 and is received by the electronic mail interface computing device 208 or a specialized application on the electronic mail interface computing device 208.

Upon processing the registration request, the electronic mail interface computing device 208 registers the mobile device client for receipt of all requested information, as authorized. As described above, if no new data is currently available for the registered client, the electronic mail interface computing device 208 does not automatically transmit a negative response to the mobile device 202. However, because the data change request remains pending and the communication link is not immediately terminated.

With reference now to FIG. 3B, in one embodiment, the electronic mail interface computing device 208 receives a notification that a data change has occurred that needs to be passed to the mobile device 202. In an illustrative embodiment of the present invention, the notification can include a notification from an electronic mail repository, such as an electronic mail server/client, that a user corresponding to the mobile device 202 has received a new electronic mail. The electronic mail interface computing device 208 transmits a notification to the mobile device 202, via the network 206, that the new data is available. In an illustrative embodiment of the present invention, the notification can include descriptive information or other criteria that may be used by the user and/or mobile device to decide whether the data will be retrieved. If the data is to be retrieved, the mobile device 202 transmits a request for data retrieval to the electronic mail interface computing device 208 in accordance with traditional and well-known data protocols, such as the Hypertext Transfer Protocol (“HTTP”), which will not be explained in greater detail. Once the data has been retrieved, the process illustrated in FIG. 3A can be repeated by the transmission of a new data registration request and time out interval by the mobile device 202.

With reference now to FIG. 3C, in another embodiment, the electronic mail interface computing device 208 continues to monitor the elapsed period time since the last communication for each registered mobile device client. If the electronic mail interface computing device 208 detects that the time out interval for registered client has expired, it transmits a notification to the mobile device 202 that the time out interval has expired and no new data notifications have been received. By transmitting the time out interval expiration notification, the electronic mail interface computing device 208 prevents the communication link with the mobile device 202 from being terminated, or dropped, by the mobile device operator 204.

As will be explained in greater detail below, upon receipt of the time out interval expiration notification, the mobile device 202 may update the previous time out interval. In an illustrative embodiment of the present invention, the mobile device 202 updates the time out interval by measuring or observing one of a variety of network conditions. The mobile device 202 then determines whether the time out interval should be adjusted based upon the measured, or observed, network conditions. Upon tuning, or adjusting, the time out interval, the mobile device 202 transmits a new registration request with the updated time out interval via the network 206. The electronic mail interface computing device 208 obtains the new request and repeats the registration process and time out clock measurement with the updated time out interval.

With reference now to FIG. 3D, in further embodiment, the mobile device 202 also monitors the time expired since the transmission of the previous registration request. If the mobile device 202 detects the expiration of the time out interval and it has not received a no new data notification from the electronic mail interface computing device 208, it assumes that communication link has been terminated or otherwise dropped. Accordingly, the mobile device 202 updates the time out interval and transmits a registration request with the updated with the updated time out interval via the network 206. The electronic mail interface computing device 208 obtains the new request and repeats the registration process and time out clock measurement with the updated time out interval. As described above, the mobile device 202 would also monitor the updated time out interval associated with the new request.

With reference to FIG. 4, a flow diagram illustrative of a routine 400 implemented by a mobile device 202 to transmit and monitor a data change request to an electronic mail interface computing device 208 in accordance with the present invention will be described. At block 402, the mobile device transmits a registration request and time out interval to the electronic mail interface computing device 208. In an illustrative embodiment of the present invention, the registration request may correspond to a selection of one or more data types, specific data files, or application programs that the mobile device may wish to receive updated information from. For example, a registration may indicate that a user wishes to receive notification when new electronic mail is received or when a particular document has been updated. The registration request may also correspond to criteria, such as rules or keywords, for selecting which data to transmit to the mobile device. The registration request can also include credentials, or other authentication information, that may be needed to receive updated information.

In accordance with an illustrative embodiment of the present invention, the time out interval information may include the specification of a fixed expiration period or length of time to be added to a current time of day. Alternatively, the time out interval information may be specified in terms of selective criteria that facilitates the generation of a time out period, or expiration period. At block 404, the mobile device 202 begins a time out clock that measures the time expired from the transmission of the registration request by mobile device 202 or the receipt of the registration request by the electronic mail interface computing device 208. The time expired can be measured in any one of a variety of manners.

At decision block 406, a test is conducted to determine whether the mobile device 202 has received a data change notification from the electronic mail interface computing device 208. If the mobile device 202 has received the data notification, at block 408, the mobile device transmits a data request to the electronic mail interface computing device 208. In an illustrative embodiment of the present invention, the data request corresponds to a request for the actual data from the electronic mail interface computing device 208, such as an HTTP data request. At block 410, the mobile device 202 obtains the requested data from the electronic mail interface computing device 208. The routine 400 then proceeds to block 416 to tune the previously provided time out interval, which will be explained in greater detail below.

Returning to decision block 406, if the mobile device 202 has not received a data change notification from the electronic mail interface computing device 208, at decision block 412, a test is conducted to determine whether the mobile device has received a time out interval expiration notification from the electronic mail interface computing device 208. If a time out interval expiration notification has been received, the routine 400 proceeds to block 416, which will be explained in greater detail below.

Returning to decision block 412, if the mobile device has not received a time out interval expiration notification from the electronic mail interface computing device 208, at decision block 414, a test is conducted to determine whether the time out interval has expired. As described above, at block 404, the mobile device measures a time expired since the transmission of the registration request. If the time out interval has not expired, the routine 400 returns to decision block 406. Alternatively, if the mobile device 202 detects that the time out interval has expired, it can assume that the electronic mail interface computing device 208 has failed to transmit a time out interval expiration notification and/or that the communication link with the electronic mail interface computing device 208 has expired.

In an illustrative embodiment of the present invention, the mobile device may also wait for an additional period of time to account for possible delays/lags in transmissions from the electronic mail interface computing device 208. Accordingly, the routine 400 then proceeds to block 416 to tune the previously provided time out interval. Block 416 will be explained in greater detail with regard to sub-routine 500 (FIG. 5). Once the time out interval has been tuned, the routine 400 returns to block 402, where the mobile device transmits a new registration request with the tuned time out interval.

With reference now to FIG. 5, an illustrative sub-routine 500 implemented by the mobile device 202 for tuning the time out interval, corresponding to block 416 (FIG. 4) will be described. In an illustrative embodiment of the present invention, the tuning of the time out interval corresponds to a comparison of a sum of a window of network communication events (e.g., consecutive tuning events) to a plurality of network confidence value thresholds based upon possible values of the same window of network communication events.

At block 502, the mobile device obtains a current time out interval and one or more threshold network confidence values. In an illustrative embodiment of the present invention, the current time out interval can correspond to a time out interval that was previously used by the mobile device. Additionally, the current time out interval can correspond to a default time out interval set by the mobile device 202, mobile device operator 204 or any other component. In an illustrative embodiment of the present invention, the threshold network confidence values correspond to a maximum threshold value that will be used to increment the current time out interval. The threshold values correspond to a minimum threshold value that will be used to decrement the current time out interval. The maximum and minimum threshold values represent a function of the maximum and minimum possible network confidence values for a given window of tuning events.

At block 504, the mobile device 202 calculates a current network confidence value for the defined window of tuning events. In an illustrative embodiment of the present invention, the mobile device 202 can take into account any number of events corresponding to network communications. The events can correspond to internal events specific to the mobile device 202. For example, the network events can include, but are not limited, to device battery life, internal measurement signal strength, processing resource utilization, user-specified criteria, and the like. The events can also correspond to external event specific to the interaction of the mobile device 202 and the network 206 and/or the network itself. For example, the events can include a dropped communication link, a transport error, transmission speed measurements, successful receipt of information, external measurement of signal strength, external component performance metrics, and the like.

In an illustrative embodiment of the present invention, each network event can be associated with a value, such as a weight, that reflects the potential effect on a communication link. In one embodiment, the values for each event can correspond to binary values of “1” for a positive event and “−1” for a negative event. In another embodiment, the values for each event can correspond to a range of values from “−1” to “1”. In such an embodiment, each network event may be accorded a weight reflective of the severity of the network event relative to other possible events. In still a further embodiment, the range of values may be all positive values with higher values reflect more positive communication link events.

To calculate a network confidence value, the sum of the weight for each event within the window of previous tuning events is calculated. In an illustrative embodiment of the present invention, the weight for each event is reduced by the time elapsed since the event occurred. Equation (1) defines the sum as follows: $\begin{matrix} {n = {\left( {\sum\limits_{j = 1}^{k}\frac{e_{j}}{t_{0} - t_{e_{j}}}} \right) + e_{0}}} & (1) \end{matrix}$

-   -   where n corresponds to the network confidence value;     -   e_(j) corresponds to a weight for each network event; and     -   t_(x) corresponds to a measurement of a time when the network         event occurred.

With continued reference to FIG. 5, at decision block 506, a test is conducted to determine whether the calculated network confidence value is above the maximum threshold. In an embodiment in which the positive, or larger value, weights represent a positive event, if the calculated network confidence values is above the threshold, the time out interval is incremented at block 508. The sub-routine 500 returns at block 510.

In an illustrative embodiment of the present invention, the time out interval may be incremented by a previously defined discrete amount. Alternatively, the time out interval may be increased in an amount proportional to the calculated network confidence value. Still further, the time out interval may be incremented by a schedule that can take into account factors such as repeated positive network events, the value of calculated network confidence, and the like. For example, the mobile device 202 may only increase the time out interval if has tracked a number of immediately preceding positive events (e.g., 5 positive events in a row). In another example, the mobile device 202 will increase the time out interval by an amount that will continuously increase according to the number of consecutive positive events. In still a further example, the mobile device 202 may increase the time out interval to a maximum amount upon tracking one or more positive events. In an illustrative embodiment of the present invention, the mobile device 202 may limit the time out interval increments to a maximum threshold, such as the mobile device operator 204 network time out interval.

If the calculated network confidence value is not above the threshold, at decision block 512, a test is conducted to determine whether the calculated network confidence value is below the minimum threshold. In an embodiment in which the negative value, or lower value, weights represent a negative event, if the calculated network confidence values is below the threshold, at block 514, the time out interval is decreased. The sub-routine 500 returns at block 516. If, however, at decision block 512, the calculated network confidence value is not below the minimum threshold, the time out interval is not adjusted and the sub-routine 500 returns at block 518.

Similar to block 508, the time out interval may be decreased by a previously defined discrete amount. Alternatively, the time out interval may be decreased in an amount proportional to the calculated network confidence value. Still further, the time out interval may be decreased by a schedule that can take into account factors such as repeated negative network events, the value of calculated network confidence, and the like. For example, the mobile device 202 may only decrease the time out interval if it has tracked a number of immediately preceding negative events (e.g., 3 negative events in a row). In another example, the mobile device 202 will decrease the time out interval by an amount that will continuously increase according to the number of consecutive negative events. In still a further example, the mobile device 202 may set the time out interval to a minimum amount upon tracking one or more negative events.

With reference now to FIG. 6, a routine 600 implemented by a network application, such as electronic mail interface computing device 208, for processing a mobile device registration request will be described. At block 602, the electronic mail interface computing device 208 obtains the mobile device registration request that includes a time out interval. At block 604, the electronic mail interface computing device 208 registers the mobile device 202 for the requested data. In an illustrative embodiment of the present invention, the registration can correspond to communication with any appropriate local network components, such as an electronic mail server, to allow the electronic mail interface computing device 208 to receive notification of new data. Additionally, the registration can correspond to the calculation of a time out interval if the registration request included criteria for calculating an appropriate time out interval. In the event that the registration request corresponds to multiple data change requests, the electronic mail interface computing device 208 can maintain a table for tracking criteria for forwarding the mobile client 202 information.

At block 606, the electronic mail interface computing device 208 begins a time out interval clock that measures the time elapsed since the receipt/processing of the registration request. In an illustrative embodiment of the present invention, the time out interval clock can correspond to an internal counting device that measures a time elapsed since the receipt of the registration request. Alternatively, the time out clock can correspond to a recordation of a time of day that the registration request was received for comparison with standard time of day measurements by the electronic mail interface computing device 208. One skilled in the relevant art will appreciate that any number of additional methodologies may be utilized to calculate, or otherwise track, a time elapsed since the receipt/processing of a registration request.

At decision block 608, a test is conducted to determine whether the electronic mail interface computing device 208 has received a notification of data change. In an illustrative embodiment of the present invention, the notification of data change can correspond to receipt of a new mail notification from an electronic mail server. Additionally, the notification of data change can correspond to a notification that a particular data file has been modified, accessed, etc. If a data change notification is received, at block 610, the electronic mail interface computing device 208 transmits a data change notification to the mobile device 202. In an illustrative embodiment of the present invention, the data change notification can include a generic message instructing the mobile device 202 to transmit a data request to the electronic mail interface computing device 208. Additionally, the data change notification can include various meta data or descriptive information that allows the mobile device 202 to select whether the device will transmit a subsequent data request. For example, the notification can include electronic mail message header information that allows the user to preview at least a portion of the message to determine whether he or she would like the entire message retrieved. In another example, the notification can include specific criteria that allow the mobile device 202 to automatically determine whether to request the change data. At block 612, the routine 600 terminates until the next registration request is received by the electronic mail interface computing device 208.

If, at decision block 608, a notification that data has changed is not received, at decision block 614, a test is conducted to determine whether a time elapsed since the receipt/processing of the registration request exceeds the time out interval. If the time out interval has not been exceeded (e.g., expired), the routine 600 returns to decision block 608. If the time out interval has expired, at block 616, the electronic mail interface computing device 208 transmits an expired time out interval notification to the mobile device 202. In an illustrative embodiment of the present invention, the expired time out interval notification corresponds to a message that maintains the communication link and that will elicit a renewed registration request by the mobile device 202. Additionally, the expired time out interval notification can include additional information, such as network event information or network characteristic information (e.g., available bandwidth, network quality ratings, etc.) that be utilized to tune subsequent time out intervals. At block 618, the routine 600 terminates.

With reference now to FIG. 7, in an alternative embodiment of the present invention, the present invention may utilize one or more additional communication channels to transmit data change notifications or time out interval expiration notifications. In accordance with this embodiment, during the data change registration request, the mobile device 202 can include notification preference information for the data change notifications and/or the time out interval expiration notification. In one example, the electronic mail interface computing device 208 can transmit data to the mobile device operator 204, which can include a specification of which communication channel to utilize for communicating with the mobile device 202. As illustrated in FIG. 7, the mobile device operator 204 can utilize a wireless data channel (e.g., an I.P. communication channel) or a short message service (“SMS”) data channel to transmit information.

In an illustrative embodiment of the present invention, the electronic mail interface computing device 208 can utilize various criteria to select which communication channel to utilize. For example, a user may specify preferences based upon time of day or size of data to be transmitted. Additionally, a user may specify cost savings preferences based on usage, data transmission bandwidth, and/or mobile operator charges. Further, the user may specify preferences based upon network criteria, such as available bandwidth or communication channel latency.

While illustrative embodiments of the invention have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the invention. 

1. A method for facilitating communication between a mobile device and a network application, the method comprising: obtaining a request for change of data, wherein the request for change of data includes a first set of expiration data for returning a response; monitoring a time interval for providing a response to the request for change of data; and transmitting a notification that no data has changed if the time interval exceeds an expiration period.
 2. The method as recited in claim 1, wherein the request for change of data corresponds to a request for new electronic mail messages.
 3. The method as recited in claim 1 further comprising: obtaining a subsequent request for change of data, wherein the request for change of data includes a second set of expiration data for returning a response; monitoring a time interval for providing a response to the subsequent request for change of data; and transmitting a notification that no data has changed if the time interval exceeds a second expiration period.
 4. The method as recited in claim 3, wherein the second set of expiration data is modified based on at least one network condition.
 5. The method as recited in claim 3, wherein the second set of expiration data corresponds to an adjustment of the first set of expiration data based upon a comparison of a sum of the weights for a set of events related to communication between the mobile device and the network application.
 6. The method as recited in claim 5, wherein the sum of the weights for the set of events corresponds to function of the weight of each event diminished by a time expired since the event occurred.
 7. A method for facilitating communications between a mobile device and a network application, the method comprising: transmitting a first request for change of data, wherein the request for change of data includes a first set of expiration data for returning a response; determining an event corresponding to the first request for change of data; generating a second set of expiration data for returning a response based upon at least one network condition; and transmitting a second request for change of data, wherein the request for change of data includes the second set of expiration data for returning a response.
 8. The method as recited in claim 7, wherein determining an event corresponding to the first request for change of data includes obtaining a notification that no data has been changed in response to the request for change of data.
 9. The method as recited in claim 7 further comprising: monitoring a time interval for receiving a response to the request for change of data; determining when the time interval exceeds an expiration period corresponding to the first set of expiration data; and determining an event corresponding to the first request for change of data has occurred based on the time interval.
 10. The method as recited in claim 7, wherein generating a second set of expiration data for returning a response based upon at least one network condition includes generating the second set of expiration data based on at least one network condition.
 11. The method as recited in claim 7, wherein the first and second set of expiration data correspond to fixed time intervals and wherein generating a second set of expiration data for returning a response based upon at least one network condition includes: associating a weight for a set of events related to communication between a mobile device and the network application; obtaining the first set of expiration data; and adjusting the first set of expiration data to generate the second set of expiration data based upon a comparison of a sum of the weights for the set of events to a set of thresholds.
 12. The method as recited in claim 11, wherein adjusting the first set of expiration data to generate the second set of expiration data based upon a comparison of a sum of the weights for the set of events to a set of thresholds includes increasing the first set of expiration data if the sum of the weights exceeds a maximum threshold.
 13. The method as recited in claim 11, wherein adjusting the first set of expiration data to generate the second set of expiration data based upon a comparison of a sum of the weights for the set of events to a set of thresholds includes decreasing the first set of expiration data if the sum of the weights exceeds a minimum threshold.
 14. The method as recited in claim 11, wherein the sum of the weights for the set of events to a set of thresholds corresponds to function of the weight of each event diminished by a time expired since the event occurred.
 15. A system for facilitating data exchange, the system comprising: one or more client devices for generating a request for change of data, wherein the request for generating a change of data includes a first expiration time period; at least one network application for receiving the request for change of data and transmitting a notification that no data has changed if a monitored time period corresponding to the first expiration time period; wherein the one or more client devices transmits a subsequent request for change of data if an event has occurred, wherein the subsequent request for change of data includes a second expiration time period.
 16. The system as recited in claim 15, wherein the one or more client devices determines an event has occurred if the client device receives a notification that no data has been changed in response to the request for change of data from the network application.
 17. The system as recited in claim 15, wherein the at least one client device generates the second expiration time period data based upon at least one network condition and wherein the at least one network condition includes at least one condition internal to a mobile device and at least one condition external to a mobile device.
 18. The system as recited in claim 15, wherein the second expiration time period corresponds to an adjustment of the first expiration time period based upon a comparison of a sum of the weights for a set of events related to communication between the mobile device and the network application.
 19. The system as recited in claim 18, wherein the sum of the weights for the set of events to a set of thresholds corresponds to function of the weight of each event diminished by a time expired since the event occurred.
 20. The system as recited in claim 15, wherein the request for change of data corresponds to a request for new electronic mail messages. 